Fueling environment wireless architecture

ABSTRACT

A method and system for transmitting data between devices within a fueling environment comprising a wireless mesh network wherein the devices are configured to communicate via the wireless mesh network. A wireless communication device is connected to each device, and a middleware executed by the wireless communication device handles communications between the devices and the wireless mesh network.

PRIORITY CLAIM

This application is a divisional of utility application Ser. No.13/452,295 filed Apr. 20, 2012 (now patented as U.S. Pat. No. 9,053,503issuing Jun. 9, 2015), which claims the benefit of provisionalapplication Ser. No. 61/477,918, filed Apr. 21, 2011 and provisionalapplication Ser. No. 61/541,548, filed Sep. 30, 2011, all of which arehereby relied upon and incorporated herein by reference for allpurposes.

FIELD OF THE INVENTION

The present invention relates generally to fueling environments. Moreparticularly, the present invention relates to a system and method forwireless communication between devices in a retail fueling environment.

BACKGROUND OF THE INVENTION

Certain retail fueling environments have incorporated wireless fidelity(“Wi-Fi”) technology to enable devices within the fueling environmentsto communicate. A Wi-Fi access point is installed in a central locationwithin the fueling environment, and each device is equipped with a Wi-Finetwork adapter configured to communicate with the Wi-Fi access point.The Wi-Fi network adapter transmits data from the associated device tothe Wi-Fi access point, which routes the data to the intended recipientdevice. Incorporating a Wi-Fi access point and network adaptersconfigured to communicate with the access point into a fuelingenvironment can incur a relatively substantial cost depending on thenumber of devices in the environment configured to communicatewirelessly. Additionally, not all devices in the fueling environment maybe configured to communicate with a Wi-Fi network adapter.

Moreover, Wi-Fi communications are susceptible to interference anddegradation caused by the surrounding environment or objects located orpositioned within the environment. For instance, objects consisting ofsubstantial amounts of liquid and/or metal can interfere with or evenabsorb the radio signals transmitted by the Wi-Fi devices. As a result,transmissions from the Wi-Fi network adapters may fail to reach theWi-Fi access point and/or the intended recipient of the data. That is, aWi-Fi network adapter and the associated access point are unable tocommunicate if the path between the two becomes interrupted.

A repeater may be positioned to receive and “repeat” data transmitted bya Wi-Fi network adapter to the access point. In such a scenario, theWi-Fi network adapter is configured to communicate directly with therepeater, which is configured to communicate directly with the accesspoint. However, the Wi-Fi communications of the system remainsusceptible to the interference, degradation, and failure describedabove. For instance, if either of the paths between the adapter and therepeater or between the repeater and the access point is interrupted,the device is unable to communicate with the intended recipient.

SUMMARY OF THE INVENTION

According to one aspect, the present invention provides a retail fuelingenvironment comprising a plurality of fuel dispensers located in aforecourt area of the fueling environment. A central controller isoperative to communicate with a remote payment authorization system toauthorize payment of fueling transactions. The fuel dispensers and thecentral controller have a respective wireless communication deviceassociated therewith such that the fuel dispensers can communicate withthe central controller via wireless transmission. Each of the wirelesscommunication devices implements a middleware program such that thewireless communication devices serve as nodes in a wireless mesh networkwherein communication between the fuel dispensers and the centralcontroller can occur via alternative transmission paths depending oncurrent conditions in the fueling environment.

In exemplary embodiments, the retail fueling environment may furthercomprise at least one fuel storage tank having a fuel level sensorassociated therewith. A further wireless communication device isassociated with the fuel level sensor and also serves as one of thenodes in the wireless mesh network. In addition, at least one of avending machine and a surveillance camera may be provided in the fuelingenvironment. The vending machine and/or surveillance camera has arespective wireless communication device also serving as a node in thewireless mesh network.

One or more repeater nodes may also be provided. Moreover,communications within the wireless mesh network may be encrypted. Thewireless communication devices may further implement a conversionprogram that allows communication between the middleware and a legacycommunication of the fuel dispensers.

A further aspect of the present invention provides a handheld device foruse in a retail fueling environment. The handheld device comprises ahousing and a touchscreen display. Circuitry located within the housingincludes a processor implementing a graphical user interface on thetouchscreen display. The circuitry further includes wirelesscommunication circuitry implementing a middleware program such that thehandheld device functions as a node in a wireless mesh network in theretail fueling environment.

According some embodiments, the processor allows the handheld device tocontrol operation of at least one fuel dispenser in the retail fuelingenvironment via the wireless mesh network. In addition, the handhelddevice may further comprise an RFID reader for reading an RFIDassociated with the fuel dispenser(s). The handheld device may also beconfigured such that real-time fueling information is shown on thetouchscreen display during a fueling transaction at the fuel dispenser.

BRIEF DESCRIPTION OF THE DRAWINGS

A full and enabling disclosure of the present invention, including thebest mode thereof directed to one of ordinary skill in the art, is setforth in the specification, which makes reference to the appendeddrawings, in which:

FIG. 1 is a schematic representation of a wireless communication devicein accordance with an embodiment of the present invention;

FIG. 2 is a partially schematic, perspective view of a fuel dispenser inaccordance with an embodiment of the present invention;

FIG. 3 is a partially schematic, perspective view of a fuelingenvironment in accordance with an embodiment of the present invention;

FIG. 4 is a partially schematic, cross-sectional representation of theinternal components of a handheld device in accordance with anembodiment of the present invention;

FIG. 5 is a front elevation view of the handheld device of FIG. 4displaying an exemplary graphical user interface;

FIG. 6 is a partially schematic, perspective view of a fuelingenvironment in accordance with an embodiment of the present invention;and

FIG. 7 is another exemplary graphical user interface displayed by thehandheld device of FIG. 4.

Repeat use of reference characters in the present specification anddrawings is intended to represent same or analogous features or elementsof the invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Reference will now be made in detail to presently preferred embodimentsof the invention, one or more examples of which are illustrated in theaccompanying drawings. Each example is provided by way of explanation ofthe invention, not limitation of the invention. In fact, it will beapparent to those skilled in the art that modifications and variationscan be made in the present invention without departing from the scope orspirit thereof. For instance, features illustrated or described as partof one embodiment may be used on another embodiment to yield a stillfurther embodiment. Thus, it is intended that the present inventioncovers such modifications and variations as come within the scope of theappended claims and their equivalents.

FIG. 1 is a schematic representation of a wireless communication device100. Wireless communication device 100 comprises a processing device102, memory 104, a transceiver 106, input-output connections (“I/O”)108, and power connections 110. Processing device 102 is operativelyconnected to memory 104, transceiver 106, and I/O 108. Wirelesscommunication device 100 may be any suitable device capable ofcommunicating within a wireless mesh network, as explained in moredetail below, such as those manufactured by Crossbow Technology Inc. ofSan Jose, Calif., Ember Corporation of Boston, Massachusetts, the BMGroup of Milan, Italy, or Telegesis Limited of Bucks, United Kingdom.

Processing device 102 may be a processor, microprocessor, controller, orother appropriate circuitry, but is preferably sized to minimize thesize of wireless communication device 100. Memory 104 may be any type ofmemory or computer-readable medium that is capable of being accessed byprocessing device 102. For instance, memory 104 may be random accessmemory (“RAM”), read-only memory (“ROM”), erasable programmable ROM(“EPROM”) or electrically EPROM (“EEPROM”), CD-ROM, DVD, or otheroptical disk storage, solid state drive (“SSD”), magnetic disk storage,including floppy or hard drives, any type of non-volatile memories, suchas secure digital (“SD”), flash memory, memory stick, or any othermedium that may be used to carry or store computer program code in theform of computer-executable programs, instructions, or data. In thecurrent embodiment, memory 104 is preferably EPROM in order to minimizethe size of wireless communication device 100. Processing device 102 mayalso include a portion of memory accessible only to the processingdevice, commonly referred to as “cache.” Thus, memory 104 may be part ofprocessing device 102, may be separate, or may be split between therelevant processing device and a separate memory device.

Memory 104 comprises computer-executable program code or instructionsthat, when executed by processing device 102, initiates a middlewareprogram that handles communication by the wireless communication deviceas described below. Memory 104 may also comprise one or more datastructures for storing information, such as a database or a table. Thecomputer-executable program code or instructions in this scenario, asshould be known to those skilled in the art, usually include one or moreapplication programs, other program modules, program data, firmware,and/or an operating system.

Transceiver 106 includes an internal radio frequency (“RF”) antennaconfigured to send and receive RF signals. Transceiver 106 incorporatesdata provided by processing device 102 into the RF signals transmittedby the antenna, which is typically accomplished by modulating a carriersignal, as should be understood in the art. Transceiver 106 is alsoconfigured to extract and transmit to processing device 102 datacontained in the RF signals received by the antenna. For simplicity, RFsignals and the data contained therein that are transmitted or receivedby transceiver 106 are referred to herein as being transmitted orreceived by wireless communication device 100.

I/O 108 provides the ability for wireless communication device 100 toelectrically connect to another device or component in order tocommunicate and transfer data with the other device. I/O 108 isconfigured to transmit data from processing device 102 to the otherdevice and to transmit data received from the other device to theprocessing device. Data transmitted or received by I/O 108 is referredto herein as being transmitted or received by wireless communicationdevice 100. The middleware program stored in memory 104 and executed byprocessing device 102 manages the communication and processing of alldata transmitted and received by the wireless communication device.

Power connections 110 are configured to provide power to wirelesscommunication device 100. In one embodiment, power connections 110 areconfigured to operatively connect to a power source external to wirelesscommunication device 100, such as a solar panel, as explained below. Itshould be understood, however, that other external powers sources may beused. For example, in a scenario where wireless communication device 100is coupled to another device, power connections 110 may be electricallycoupled to the device's power supply. Alternatively, wirelesscommunication device 100 may include an internal battery coupled topower connections 110 in order to provide power to the device. Thebattery may be rechargeable, which may be accomplished via an externalpower supply that connects directly to power connections 110 orindirectly via I/O 108, as explained below. Alternatively, the batterymay be recharged via induction by placing power connections 110 adjacentto an inductive charging station.

FIG. 2 is a partially schematic perspective view of a fuel dispenser 200comprising a user interface 202, a processing device 204, and memory206. User interface 202 includes a display 208, a card reader 210, and anumeric pad 212. Processing device 204 is operatively connected tomemory 206, as well as the components of user interface 202, includingdisplay 208, card reader 210, and numeric pad 212. User interface 202may comprise other components operatively connected to processing device204, such as a smart card reader, a cash acceptor, and/or a receiptprinter, as should be understood in the art. Fuel dispenser 200additionally comprises wireless communication device 100, which isoperatively connected to processing device 204. That is, an electricalcommunication path exists between I/O 108 (FIG. 1) of wirelesscommunication device 100 and processing device 204.

Processing device 204 may be a processor, microprocessor, controller,microcontroller, or other appropriate circuitry. For example, multipleelectronic devices configured to operate together within fuel dispenser200 may be considered a “processing device.” Memory 206 may be any typeof memory or computer-readable medium that is capable of being accessedby processing device 204, including the examples set forth above withrespect to memory 104 of FIG. 1. Memory 206 comprisescomputer-executable program code or instructions that, when executed byprocessing device 204, control the components of fuel dispenser 200including user interface 202 to perform certain tasks and processes asdescribed in more detail below.

As should be understood by those of ordinary skill in the art, fueldispenser 200 also includes various components configured to facilitatethe delivery of fuel to a vehicle. For instance, fuel dispenser 200additionally comprises a piping network 214 in fluid communication withat least one underground storage tank (“UST”), a meter 216, a pulser218, a valve 220, a hose 222, and a nozzle 224. Processing device 204 isoperatively connected to one or more of these components, such as pulser218 and valve 220, in order to control their operation and to manage thedelivery of fuel by fuel dispenser 200.

User interface 202 is configured to facilitate the dispensing of fueland the acceptance of payment for the dispensed fuel, as should beunderstood in the art. For instance, display 208 is configured toprovide instructions to a customer regarding the fueling process, whilecard reader 210 and numeric pad 212 are configured to accept paymentcard information provided by the customer. That is, card reader 210 isconfigured to receive payment card data from a magnetic stripe card,such as a credit or debit card, that is swiped or inserted into the cardreader. Numeric pad 212 is configured to receive information from acustomer associated with the swiped card, such as a personalidentification number (“PIN”) of a debit card or the billing zip code ofa credit card. If included within user interface 202, other devices areconfigured to facilitate financial transactions for payment of thedispensed fuel. For instance, the smart card reader is configured tohandle transactions involving the use of smart cards, while the cashacceptor is configured to handle transactions involving cash payments.The receipt printer is configured to print a receipt upon completion ofa fueling process, as described below. Processing device 204 isconfigured to handle the communication and processing of all datatransmitted to and received from the components of user interface 202.

It should be understood that user interface 202 may also be configuredto exchange information with a customer unrelated to the fuelingtransaction. For instance, display 208 may be configured to provideadvertisements or other information to the customer, such as thatregarding nearby hotels and restaurants. Numeric pad 212 may beconfigured to receive a selection from the customer regarding thedisplayed information, such as whether the customer is interested innearby amenities.

Wireless communication device 100 is configured to enable fuel dispenser200 to communicate with a wireless mesh network, as explained below.Preferably, wireless communication device 100 handles the communicationof data transmitted to and from fuel dispenser 200. Processing device204 is configured to transmit data to and receive data from wirelesscommunication device 100 via the electrical communication pathconnecting the processing device and the wireless communication device.Accordingly, data transmitted and received by wireless communicationdevice 100 via the wireless mesh network is referred to herein as beingtransmitted and received by fuel dispenser 200 for purposes of thefollowing explanation.

FIG. 3 is a perspective view of a fueling environment 300 adapted toprovide fuel to a customer and to accept payment for the dispensed fuel.Fueling environment 300 comprises at least one fuel dispenser 200 alocated in a forecourt region of the fueling environment, and a centralfacility 302. Typically, one or more additional fuel dispensers, such asfuel dispenser 200 b, may also be located in fueling environment 300.The fuel dispensers of fueling environment 300 are preferably similar inconstruction and operation to fuel dispenser 200 of FIG. 2. Fueldispensers 200 a and 200 b comprise wireless communication devices 100 aand 100 b, respectively. In the presently-described embodiment, fuelingenvironment 300 also includes a canopy structure 304 connected tocentral facility 302 that provides shelter to fuel dispensers 200 a and200 b, as should be understood in the art.

Central facility 302 comprises a point-of-sale device (“POS”) 306 and asite controller 308 and may include additional computers, such ascashier and/or manager workstations. It should be understood that thefunctionality of POS 306, site controller 308, and any additionalcomputers within central facility 302 may be incorporated into a singlecomputer or server. In the embodiment illustrated, POS 306 comprises anassociated card reader and payment terminal 310. Each of POS 306 andsite controller 308 may also include a display, a touch screen, and/orother input devices.

In one embodiment, POS 306 and site controller 308 are operativelyconnected to a local area network (“LAN”) via a wired or wirelessconnection, as should be understood in the art. A device typicallylocated within central facility 302 is operatively connected to the LANand to a wide area network (“WAN”), such as the Internet. The devicefacilitates communication of the other devices connected to the LAN, aswell as communication with devices external to fueling environment 300that are connected to the WAN, as should also be understood. In oneembodiment, the device is a standalone router, switch, or gateway,although it should be understood that either POS 306 or site controller308 may additionally perform the functions of, and therefore replace,such a device.

In another embodiment, POS 306 and site controller 308 are operativelyconnected to wireless communication devices 100 c and 100 d,respectively, as illustrated in FIG. 1 and explained in more detailbelow. Alternatively, each of POS 306 and site controller 308 may beconnected to the LAN, an associated wireless communication device, orboth.

As is well-known, at least one server external to fueling environment300 and maintained by a third-party, such as a financial institution, isconnected to the WAN. It should be understood that fueling environment300 may be operatively connected via the WAN to several serversmaintained by various financial institutions in order to carry outfinancial transactions involving customer accounts maintained by thedifferent financial institutions.

Fueling environment 300 may additionally comprise one or more standalonewireless communication devices, such as wireless communication devices100 e and 100 f. In one embodiment, wireless communication device 100 fis attached to the underside of canopy structure 304. A solar panel maybe attached to the top surface of canopy structure 304 and connected towireless communication device 100 f in order to provide a source ofpower to the wireless communication device.

As should be understood in the art, fueling environment 300 additionallycomprises components necessary for delivering fuel to customers'vehicles. For example, fueling environment 300 comprises one or moreUSTs, such as tanks 312 and 314. USTs 312 and 314 are in fluidcommunication with dispensers 200 a and 200 b via an underground pipingnetwork 316 and the dispensers' piping networks 214 (FIG. 2). Each ofUSTs 312 and 314 are connected to at least one sensor, such asrespective sensors 318 and 320, in order to measure and/or determinecertain characteristics of the UST, including the volume of fuel and thepressure within the respective UST. Wireless communication devices 100 gand 100 h are operatively connected to sensors 318 and 320,respectively.

Fueling environment 300 may comprise other components, such as lights,air conditioning units, security systems, car wash equipment, andvending machines. A wireless communication device may be operativelyconnected to each such component in order to enable the component tocommunicate via the fueling environment's wireless mesh network asexplained in more detail below. Fueling environment 300, for example,further comprises a vending machine 322, which is operatively connectedto a wireless communication device 100 i. In this example, fuelingenvironment 300 also comprises a surveillance camera 324, which may beoperatively connected to a security system, the LAN, a wirelesscommunication device, such as device 100 e, or any combination thereof.

Each wireless communication device connected to a device within fuelingenvironment 300 is operatively connected to that device's processingdevice in a manner similar to that described above with respect toprocessing device 204 and wireless communication device 100 of fueldispenser 200 illustrated in FIG. 2. Likewise, the wirelesscommunication device is configured to enable the associated device tocommunicate with a wireless mesh network, as explained below.Accordingly, data transmitted and received by the wireless communicationdevice via the wireless mesh network is referred to herein as beingtransmitted and received by the respective device for purposes of thefollowing explanation. For instance, data output by vending machine 322to the wireless mesh network via wireless communication device 100 i isreferred to herein as being transmitted by the vending machine.Additionally, the wireless communication devices located within fuelingenvironment 300 are similar in construction and operation to wirelesscommunication device 100 of FIG. 1. However, it should be understoodthat while the middleware of each wireless communication device isidentical, it provides differing functionality depending on the type ofdevice to which the respective wireless communication device isconnected. For example, the middleware of wireless communication devices100 a and 100 b is configured to provide functionality corresponding totransactions carried out by fuel dispensers 200 a and 200 b, while themiddleware of wireless communication devices 100 g and 100 h isconfigured to provide functionality corresponding to the measurementstaken by sensors 318 and 320.

The wireless communication devices of fueling environment 300 create awireless mesh network in order to enable the devices within theenvironment to communicate. Each wireless communication device isconsidered to be a node in the wireless mesh network and configured tocommunicate with any other node in the wireless mesh network. That is,each wireless communication device is configured to receive, handle, andtransmit data over the wireless mesh network. Examples of suitablewireless mesh networks are those adhering to the IEEE 802.15.4-2006standard, including the ZigBee and MiWi specifications, all of which areincorporated by reference for all purposes as if set forth verbatimherein.

It should be understood that the wireless communication devices offueling environment 300 are relatively small, inexpensive, and consume arelatively small amount of power when operating. As a result, thewireless communication devices may be placed throughout fuelingenvironment 300 and connected to various power supplies in order tocreate a consistent and reliable wireless mesh network. The transmissionrange for each node is approximately 15 to 100 meters or 50 to 330 feet,depending on the type of wireless communication device used. It shouldbe further understood that nodes are installed and located withinfueling environment 300 so that any radio signal transmitted fromdefined locations within the environment will be received by thewireless mesh network. For instance, wireless communication devices thatare not connected to a device of fueling environment 300, such aswireless communication device 100 f, are configured to merely retransmitany data received via the wireless mesh network. It should be understoodthat these wireless communication devices increase the coverage of thewireless mesh network.

In one embodiment, one of the wireless communication devices of thewireless mesh network acts as a coordinator. That is, the coordinatormaintains information that defines the wireless mesh network andidentifies its nodes. The coordinator transmits this information to theother nodes when requested or needed. For instance, the coordinatormaintains a table of available nodes connected within the wireless meshnetwork. The other nodes may be configured to store a copy of thisinformation, after which the coordinator only transmits changes to theconfiguration of the wireless mesh network, such as the addition orremoval of a node to the network. It should be understood that any ofthe wireless communication devices of fueling environment 300 may beconfigured to operate as the coordinator.

Based on the information provided by the coordinator, the nodes of thewireless mesh network transmit data via the network in the mostefficient manner and path depending on certain characteristics of thetransmitting and receiving nodes, such as their respective locations.While a network administrator may configure the manner and paths bywhich data is transmitted via the wireless mesh network, the wirelessmesh network is configured to transmit data using the least number ofavailable nodes by default in the presently-described embodiment.Alternatively, the nodes of the wireless mesh network may be configuredto transmit data using table routing or using “ad hoc on demand distancevector routing” (“AODV”).

In another embodiment, each node of the wireless mesh network stores acopy of a database or a table comprising information representative ofthe nodes operatively connected to the network. The informationcorresponding to the nodes is maintained in real-time so that anychanges to the database are populated throughout the network to eachnode. In this embodiment, the middleware executed by each node isresponsible for determining the most efficient manner and path by whichdata should be transmitted by the node. This may be accomplished byselecting the fewest number of available nodes, by table routing, or byAODV, as set forth above.

The wireless mesh network of fueling environment 300 is configured to beredundant, reliable, and self-healing. That is, if one node becomesinaccessible or unavailable for any reason, such as due to the placementof a large metal object adjacent the node, the wireless mesh networkroutes data via the network using the other available nodes. Forexample, data output by fuel dispenser 200 b to site controller 308 maybe transmitted via the wireless mesh network from wireless communicationdevice 100 b to wireless communication device 100 d via wirelesscommunication device 100 f and/or 100 e should devices 100 b and 100 dbe unable to communicate directly. If a communication path usingwireless communication device 100 f and/or 100 e is unavailable,wireless communication device 100 b may communicate with wirelesscommunication device 100 d via one or more of wireless communicationdevices 100 a, 100 h, 100 g, and 100 i. It should be understood that themiddleware of each wireless communication device determines the bestcommunication path to the intended recipient upon receiving dataregardless of the path by which the data was delivered to the node.

In one embodiment, a node sending data via the wireless mesh networkattaches a header to the data that provides information about therecipient node. The header may be configured to include datacorresponding to the transmitting node as well. Any intermediate nodereceiving the transmission identifies the intended recipient node fromthe data contained in the header. It is possible for the node to receivethe data from several nodes depending on the configuration of thewireless mesh network. The node determines the manner by which the datashould be transmitted based on the identification of the destinationcontained in the header. In one embodiment, the node uses theinformation contained in the header to determine if it has alreadyreceived the data. If so, the receiving node discards any additionalcopies of the data it receives.

In another embodiment, a node transmitting data via the wireless meshnetwork includes an acknowledgement request in the data. The requestdirects a node that receives the request to return an acknowledgementletting the node sending the transmission know that it has beenreceived. Upon receipt of the acknowledgement, the sending node ceasestransmitting the data. Each node that receives the data returns such anacknowledgement to the node from which the data was received.

In yet another embodiment, a checksum is transmitted along with the datato enable any recipient nodes to determine whether the entire set ofdata was received. If not, the recipient node informs the sending nodeto retransmit the data. This process repeats itself until the receivingnode verifies that it has received the entire set of data using thechecksum.

Referring to FIGS. 2 and 3, in operation, a customer positions hisvehicle adjacent to fuel dispenser 200 a to initiate the fuelingprocess. Display 208 presents instructions to the customer as to themanner by which to begin the process, which may instruct the customer toswipe a credit or debit card using card reader 210. In this example, thecustomer swipes a debit card using card reader 210 and provides his PINto dispenser 200 a using numeric keypad 212. In order to determinewhether to authorize the fueling process, fuel dispenser 200 a transmitsat least a portion of the payment card data received from the customerto site controller 308 via the wireless mesh network. That is, wirelesscommunication device 100 a transmits the data to wireless communicationdevice 100 d via the wireless mesh network.

Site controller 308 transmits at least a portion of the informationreceived from fuel dispenser 200 a to the server of the financialinstitution connected to the WAN that maintains the accountcorresponding to the card supplied by the customer. The financialinstitution either authorizes or denies the transaction based on thetransmitted information and returns data representative of the decisionto site controller 308. Site controller 308 transmits data indicatingwhether the financial institution authorized the fueling transaction tofuel dispenser 200 a via the wireless mesh network.

If fuel dispenser 200 a receives an authorization from site controller308, processing device 204 instructs valve 220 to open in order to allowthe flow of fuel. When the customer activates nozzle 224 and valve 220is open, fuel flows from at least one of USTs 312 and 314 to pipingnetwork 214 (FIG. 2) of fuel dispenser 200 a via underground pipingnetwork 316. Meter 216 measures the flow of fuel as it flows through themeter, while pulser 218 transmits a signal to processing device 204representative of the measurement.

Upon completion of the fueling process, fuel dispenser 200 a transmitsdata to site controller 308 via the wireless mesh network, such as theamount of fuel delivered to the customer's vehicle. Site controller 308then transmits at least a portion of the data to the applicablefinancial institution via the WAN in order to complete the transaction.The financial institution performs any necessary tasks which may includedebiting the customer's account, as is well-known in the art.Additionally, site controller 308 may transmit data to fuel dispenser200 a via the wireless mesh network in order to complete any ancillarytasks associated with the fueling process (such as printing a receipt atthe dispenser) for the customer if desired.

Other wireless communication devices of fueling environment 300 areconfigured to handle communication of data representative of informationreceived from the device to which the respective wireless communicationdevice is connected. For example, wireless communication devices 100 gand 100 h transmit data representative of information received fromsensors 318 and 320, respectively, regarding the fuel contained inrespective USTs 312 and 314. In one embodiment, sensor 318 constantlymeasures the volume of fuel contained in tank 312 and outputs datarepresentative of the measurements to wireless communication device 100g. Wireless communication device 100 g transmits the data to wirelesscommunication device 100 d of site controller 308 via the wireless meshnetwork.

By way of another example, sensor 320 monitors UST 314 to detect anymalfunction by the tank or parts associated therewith. If a malfunctionis detected, sensor 320 outputs data representative of the malfunctionto wireless communication device 100 h, which transmits the data to sitecontroller 308 via the wireless mesh network in order to be handledappropriately. Additionally, camera 324 may be configured to outputdata, which may include video footage filmed and streamed by the camera.In such an embodiment, camera 324 outputs the data to wirelesscommunication device 100 e which transmits the data via the wirelessmesh network.

In another embodiment, one of the wireless communication devices of thefueling environment is configured to connect directly to the WAN orindirectly to it by being operatively connected to the LAN directly. Thewireless communication device handles communications between thewireless mesh network and resources connected to the WAN that areexternal to fueling environment 300. For example, wireless communicationdevice 100 e may be configured to connect to the WAN directly andfunction as a gateway. In such an embodiment, wireless communicationdevice 100 e is referred to as gateway 100 e. Gateway 100 e continues tofunction as a node in the wireless mesh network. That is, gateway 100 econtinues to send and receive data via the wireless mesh network, suchas the data transmitted by fuel dispenser 200 a and intended for sitecontroller 308. Gateway 100 e is also configured to route information toany wireless communication device that has requested information fromremote devices located on the WAN in a manner similar to a router orgateway.

For example, wireless communication device 100 i may be configured totransmit data representative of information provided by vending machine322 via the wireless mesh network to a resource external to fuelingenvironment 300 and connected to the WAN. In one embodiment, vendingmachine 322 is configured to output data representative of the vendingmachine's usage to a server connected to the WAN and associated with thevending machine operator. The vending machine's processing deviceoutputs this data to wireless communication device 100 i, whichtransmits the data to gateway 100 e via the wireless mesh network.Gateway 100 e transmits the data to the remote server via the WAN.Gateway 100 e transmits any data returned from the server and intendedfor vending machine 322 to wireless communication device 100 i via thewireless mesh network.

In another embodiment, vending machine 322 is configured to transmit anotification to the external server when its inventory drops below apredetermined amount. In a manner similar to that described above,wireless communication device 100 i transmits the notification to theserver via the wireless mesh network, gateway 100 e, and the WAN.

In another embodiment, fuel dispensers 200 a and 200 b are configured tohandle the financial transactions for the fuel provided by thedispensers. In this embodiment, fuel dispensers 200 are configured tocommunicate directly with the financial institution rather than sendingfinancial information to site controller 308 to be communicated to thefinancial institution. Fuel dispensers 200 a and 200 b transmit paymentcard data to gateway 100 e via the wireless mesh network, whichtransmits the data to the financial institution via the WAN. Any datareturned by the financial institution is routed by gateway 100 e to thefuel dispensers via the wireless mesh network. The process thencontinues in a manner similar to that described above.

It should be understood that fuel dispensers 200 a and 200 b maycontinue to transmit data representative of the transactions carried outby the dispensers to site controller 308 for reporting or other purposesin the presently-described embodiment. In fact, fueling environment 300may be configured so that only non-sensitive/confidential paymentinformation is transmitted to site controller 308. As a result, sitecontroller 308 would not be required to comply with certain securityrequirements. An example of such a fueling environment is described incopending U.S. patent application Ser. No. 12/689,983 entitled “PaymentProcessing System for Use in a Retail Environment Having SegmentedArchitecture,” the entire disclosure of which is hereby incorporated byreference for all purposes as if set forth verbatim herein.

In one embodiment, the wireless communication devices are configured toencrypt data transmitted by the devices and decrypt data received by thedevices. The wireless communication devices may utilize the 128-bitAdvanced Encryption Standard (“AES”), although it should be understoodthat other suitable encryption standards and schemes may be used. Itshould also be understood that the wireless communication devices may beconfigured to encrypt only sensitive or confidential data rather thanany data transmitted by the device. In such an embodiment, the devices'middleware is preconfigured to determine what data should be encryptedprior to transmission.

Referring to FIGS. 1 and 3, in another embodiment, memory 104 of eachwireless communication device comprises computer-executable program codeor instructions that, when executed by processing device 102, executes aconversion component that handles communication between legacy ornon-standard devices and the middleware. That is, the conversioncomponent enables the middleware and devices to communicate that are notnatively configured to communicate with one another. For instance, afuel dispenser that has been in service for a relatively extended amountof time may not be configured to natively communicate with themiddleware described above. Instead, the fuel dispenser may beconfigured to send and receive data using only two wires or via a serialport, such as one configured to use the RS232 standard. Thecommunication output apparatus of the device, such as the two wires oran RS232 serial port, is operatively connected to I/O 108 of wirelesscommunication device 100 in a manner similar to that described abovewith respect to the electrical communication path between processingdevice 204 and wireless communication device 100 of FIG. 2.

The conversion component stored within memory 104 and executed byprocessing device 102 manages communication between the legacy deviceand wireless communication device 100. In this example, for instance,the conversion component interprets any data transmitted via thedispenser's wires into data that can be used by the middleware. Theconversion component then outputs the data in a format understood by themiddleware. Additionally, the conversion component translatesinstructions or commands directed to the legacy or non-standard devicefrom the middleware into commands understood by the device. For example,the conversion component converts an authorization received by wirelesscommunication device 100 into one or more signals recognized by thedispenser as an authorization. The conversion component then outputs theauthorization to the dispenser using the two wires, serial port, or anyother suitable data connection. In this manner, the conversion componentenables devices and the middleware to communicate when they are notnatively configured to do so. As a result, legacy or non-standarddevices are able to interact with the wireless communication devices andutilize the wireless mesh network.

FIGS. 4 and 5 illustrate an exemplary handheld device 400 configured tointeract within the fueling environment. FIG. 4 is a partiallyschematic, cross-sectional representation of the internal components ofhandheld device 400, while FIG. 5 is a front elevation view of thehandheld device. Referring to FIG. 4, handheld device 400 comprises anenclosure 402 defining an internal area that includes a circuit board404. Circuit board 404 comprises a processing device 406, memory 408, atransceiver 410, and a data connection 412. Handheld may compriseadditional components, such as a memory slot 414, a vibration unit 416,and a speaker 418. Those of ordinary skill in the art should understandthat other components may be included within handheld device 400 asdesired or needed, such as a microphone as explained below. Processingdevice 406, memory 408, and transceiver 410 are similar in constructionand operation to processing device 102, memory 104, and transceiver 106,respectively, of wireless communication device 100 described above withrespect to FIG. 1. Accordingly, data transmitted by processing device406 to transceiver 410, which modulates a carrier signal to contain thedata and transmits the resulting RF signal, is referred to as beingtransmitted by handheld device 400. Likewise, data contained in RFsignals received by transceiver 410 and transmitted to processing device406 for handling is referred to herein as being received by handhelddevice 400. In this embodiment, processing device 406 is alsooperatively connected to memory slot 414, vibration unit 416, andspeaker 418.

Enclosure 402 is encased in a housing cover 420 preferably constructedfrom a plastic or rubberized material in order to protect handhelddevice 400 in the event it is dropped or from other shocks caused byunexpected impacts. Rubberized housing cover 420 also prevents thecreation of sparks should the handheld device be dropped or come intocontact with metal. Additionally, rubberized cover 420 is preferablyconstructed from an anti-static material in order to prevent the buildupof electrical energy. Enclosure 402 is preferably an airtight enclosuresuch that circuit board 404 located within the enclosure is shieldedfrom external factors, and the housing's interior is separated from theenvironment. For example, any electrical occurrence or discharge, suchas a spark produced by circuit board 404, is contained within handhelddevice 400. As a result, such an airtight, anti-shock, antistatichandheld device is preferably in compliance with the applicable“Atmospheres Explosibles,” or “ATEX,” Directives.

Data connection 412 is an I/O connection that allows data to betransmitted to processing device 406 via the connection. In oneembodiment, data connection 412 is contained within enclosure 402, suchthat cover 420 must be removed and the enclosure opened in order to gainaccess to the connection. In another embodiment, enclosure 402 and cover420 define corresponding apertures through which access to dataconnection 412 is provided. In such an embodiment, the enclosure 402 maycomprise a sealing gasket in order to maintain the enclosure's airtightcharacteristics. In another embodiment, a portion of cover 420 isconfigured to seal in place with the rest of the cover over theapertures. That is, cover 420 may be segmented so that the portioncovering the apertures may be pulled away from the aperture, therebyproviding access to the data connection. Cover 420 is designed such thata sufficient amount of force applied to the portion seals it back inplace with the rest of the cover.

In the presently-described embodiment, data connection 412 is auniversal serial bus (“USB”) port capable of sending and receiving data,as well as receiving power. In one embodiment, data connection 412 isconfigured to provide a sufficient amount of power in order for handhelddevice 400 to operate. In another embodiment where handheld device 400comprises an internal rechargeable battery, data connection 412 may beconfigured to handle an amount of power sufficient to recharge thebattery. Additionally, handheld device 400 may be connected to anothercomputer or server, such as site controller 308, via data connection 412and a USB cable in order to update the handheld device's firmware,software, and/or GUIs stored in memory 408, to send and receive otherdata to and from the handheld device, or to recharge the handhelddevice's internal battery.

Optional memory slot 414 is configured to accept removable memorydevices, such as a secure digital device, flash memory, or a memorystick. Memory slot 414 is configured to allow processing device 406 tostore data on the removable memory device so that the data may beremoved or copied from the handheld device without affecting thedevice's operation. In one embodiment, processing device 406 isconfigured to store data representative of logs, images, and varioususer configurations for handheld device 400, such as the preferences ofeach operator of the handheld device. Memory slot 414 may also beconfigured to transmit data stored on removable media to processingdevice 406. For instance, the firmware stored in memory 408 may beupdated with a new version stored on the media inserted into memory slot414.

Referring to FIG. 5, handheld device 400 further comprises a touchscreen 500, soft buttons 502, and numeric pad buttons 504, all of whichare operatively connected to processing device 406. Buttons 502 and 504preferably comprise sealing gaskets in order to maintain the airtightcharacteristic of enclosure 402 described above. Touch screen 500 isconfigured to display graphical user interfaces (“GUIs”) comprisingvarious buttons and indicia. FIG. 5 illustrates an exemplary GUI 508comprising a plurality of buttons commonly denoted at 510 and anindication area 512. It should be understood that the GUIs may beconfigured to display various buttons, icons, indicia, and information.An operator of handheld device 400 interacts with the device using touchscreen 500, soft buttons 502, and numeric pad buttons 504. For instance,the operator activates handheld device 400 by depressing one of softbuttons 502 for a selected period of time, while numeric pad buttons 504may be used to effect financial transactions within fueling environment300 as described below. The arrangement and operation of severalexemplary GUIs presented by touch screen 500 are described in moredetail below.

Touch screen 500, vibration unit 416, and speaker 418 may be configuredto provide an indication when the handheld receives data. For instance,if data is received by transceiver 410 and/or data connection 412, touchscreen 500 may display a visual indication that the data has beenreceived. In another embodiment, processing device 406 instructsvibration unit 416 to vibrate when data is received. In yet anotherembodiment, speaker 418 is configured to output an audible alert whendata is received. It should be understood that handheld device 400 maybe configured to output any combination of these alerts when data isreceived.

In another embodiment, speaker 418 is configured to output audiblemessages transmitted to handheld device 400 by an administrator ormanager from within central facility 302 (FIG. 3) via the wireless meshnetwork. Additionally, in an embodiment where handheld device 400comprises a microphone, the speaker and microphone allow the handhelddevice to be used in an intercom system, thereby allowing a managerinside central facility 302 and operators of the handheld devices tocommunicate. It should also be understood that the operators of thehandheld devices may communicate with one another if desired. Moreover,the touch screen, speaker, and microphone allow handheld device 400 tobe used as a mobile communication device, such as a mobile cellular orInternet phone.

In one embodiment, handheld device 400 comprises an internalrechargeable battery configured to supply power to the handheld, similarto that described above with respect to wireless communication device100 of FIG. 1. The internal battery may be recharged via a connection toan external power supply or to data connection 412 or by induction.Those of ordinary skill in the art should appreciate that an embodimentwere the internal battery of handheld device 400 is rechargeable viainduction allows enclosure 402 to be manufactured without an openingnecessary for the handheld to connect to an external power supply. Itshould be further appreciated that such an embodiment facilitatesmaintaining the airtight characteristics of handheld device 400.

Memory 408 of handheld device 400 includes the middleware describedabove that, when executed by processing device 406, enables handhelddevice 400 to send and receive data via the wireless mesh network of thefueling environment. Memory 408 additionally comprises computerinstructions or code that, when executed by processing device 406,controls the operation of touch screen 500, as well as the handhelddevice's other components, in order to perform the functions describedbelow. Upon execution of the computer code, for instance, touch screen500 displays GUI 508 that allows an attendant to interact with thedevices within fueling environment 300, such as fuel dispensers 200 aand 200 b, and to facilitate transactions involving components of theenvironment.

Referring to FIGS. 4, 5, and 6, for example, GUI 508 providesinformation about, and displays buttons or indicia representative of,components located within fueling environment 300. In this example,buttons 514, 516, 518, and 520 correspond to the fuel dispensers, button522 corresponds to a car wash, button 524 corresponds to the lights, andbuttons 526 and 528 correspond to the security system of fuelingenvironment 300. GUI 508 may include additional indicia to provide theoperator with information, such as wireless indicia 530 that provides anindication of the strength of the radio field of the wirelesscommunication device closest to handheld device 400. It should beunderstood that GUI 508 may be adapted to display a button for eachcomponent in the fueling environment with which the operator mayinteract, including vending machine 322 and USTs 312 and 314.

Referring to FIGS. 5 and 6, for example, attendant 600 selects theindicia or button representative of the fuel dispenser located adjacentto a customer's vehicle, such as button 514 corresponding to fueldispenser 200 a. Touch screen 500 displays a GUI configured for thecomponent within fueling environment 300 corresponding to the buttonselected by the operator. The GUI associated with the component providesinformation to the operator corresponding to the component, as well asthe ability to interact with the component. It should be understood thatthe GUI for each component within fueling environment 300 may beconfigured specifically for the respective component since each type ofcomponent may operate uniquely and perform different functions. Forinstance, the GUI configured to allow attendant 600 to interact with thefuel dispensers differs from the GUIs configured to allow the operatorto interact with the car wash or the security system.

FIG. 7, for example, illustrates a GUI 700 configured to allow attendant600 to interact with fuel dispenser 200 a. Touch screen 500 displays GUI700 upon activation by attendant 600 of button 514 of GUI 508 (FIG. 5).GUI 700 comprises a component indication area 702, a componentinformation area 704, an action area 706, and a component selection area708. Component indication area 702 identifies the component to which theGUI currently displayed by the handheld device corresponds. Componentinformation area 704 provides information received from or related tothe component to which the GUI corresponds. Action area 706 displaysbuttons and/or other indicia that allow the operator to send commandsto, instruct, or control the component to which the GUI corresponds.Action area 706 may also include buttons that allow attendant 600 tocarry out transactions associated with the fueling environment.Component selection area 708 displays buttons and/or other indicia thatallow the operator to select other components within the fuelingenvironment and to display the GUI associated with the selectedcomponent. In this example, selection area 708 comprises buttons oraction items similar to those presented by GUI 508 (FIG. 5), therebyproviding the ability to select and interact with the environment'scomponents other than the one currently selected.

In the presently-described embodiment, component identification area 702identifies fuel dispenser 200 a as the currently-selected component (towhich GUI 700 corresponds). Component information area 704 displaysinformation provided by or relevant to fuel dispenser 200 a. Suchinformation may include the total value of the volume of fuel that hasbeen or is currently being dispensed, the total volume of fuel that hasbeen or is currently being dispensed, and the price per unit volume ofthe type of fuel that has been or is currently being dispensed.

In this example, action area 706 comprises a stop button 710, a receiptbutton 712, a card payment button 714, and a cash payment button 716.Stop button 710 is configured to allow attendant 600 to terminate thecurrent fueling process for any reason if one is in progress. Receiptbutton 712 is configured to allow attendant 600 to print a customerreceipt for the corresponding fueling process. If a fueling process hasbeen completed, card payment button 714 is configured to allow attendant600 to accept and process a credit or debit card provided by thecustomer as payment for the dispensed fuel. Cash payment button 716 isconfigured to allow attendant 600 to accept and process a cash paymentreceived from the customer as payment. It should be understood thataction area 706 may comprise additional action items or buttons asneeded or desired and that certain buttons or action items may bedisabled depending on the current circumstances. For example, buttons712, 714, and 716 may be inactive or disabled until the current fuelingprocess has been completed or is terminated. It should also beunderstood that each button or action item may cause handheld device 400to present additional GUIs. For instance, activation of receipt button712 may cause handheld device 400 to present a GUI configured to allowattendant 600 to select a specific printer located within the fuelingenvironment to print the receipt should the environment comprise morethan one printer. In this embodiment, the indicia area of GUI 700includes wireless indicia 530, as well as a battery meter indicia 718that indicates the remaining battery life of the handheld device.

Referring to FIGS. 5, 6, and 7, in operation, a customer positions avehicle adjacent to fuel dispenser 200 a and approaches attendant 600 inorder to initiate a fueling transaction involving the dispenser. Thecustomer provides attendant 600 with a form of payment, such as cash ora credit or debit card. Attendant 600 uses handheld device 400 to accessGUI 508 displayed by touch screen 500. Attendant 600 selects the buttonor indicia on the GUI corresponding to the fuel dispenser selected bythe customer, which is button 514 corresponding to fuel dispenser 200 ain this example.

Attendant 600 then selects the button corresponding to the type ofpayment provided by the customer, such as button 714 if the customerprovided a credit or debit card or button 716 if the customer providedcash as the form of payment. Handheld device 400 is configured todisplay additional GUIs depending on the button selected by attendant600. For instance, if attendant 600 selected button 714, handheld device400 may present a GUI configured to allow the attendant to enter theaccount number of the credit or debit card and any other necessaryinformation. Alternatively, attendant 600 may utilize numeric padbuttons 504 to enter the account number of the card. The customer may beasked to enter the PIN or billing postal code associated with theaccount, which may be accomplished via numeric pad buttons 504 or touchscreen 500. Alternatively, if attendant 600 selected button 716,handheld device 400 may display a GUI configured to allow the attendantto input the amount of currency provided by the customer using touchscreen 500 or numeric pad buttons 504.

Handheld device 400 transmits data representative of the financialinformation provided by the customer to site controller 308 via thewireless mesh network. As explained above, the middleware executed byprocessing device 406 determines the best available transmission pathfrom handheld device 400 to site controller 308, which may includewireless communication devices 100 f, 100 e, and 100 c or which may bedirectly from the handheld device to wireless communication device 100d. Site controller 308 determines whether fuel dispenser 200 a should beauthorized for use by the customer in a manner similar to that describedabove. Site controller 308 transmits data representative of thedetermination to fuel dispenser 200 a via the wireless mesh network. Thefueling process then proceeds in the manner described above. In oneembodiment, fuel dispenser 200 a transmits real-time data correspondingto the fueling process via the wireless mesh network to handheld device400, which is displayed by touch screen 500.

Once the fueling process is complete, fuel dispenser 200 a transmitsdata representative of the completed transaction to site controller 308.Site controller 308 may perform a number of functions, such as storinginformation corresponding to the transaction in a log or a report, asshould be understood in the art. Site controller 308 then transmits atleast a portion of the data to handheld device 400 in order to completethe transaction. For example, site controller 308 may transmit datacontaining the total volume of fuel associated with the transaction anda transaction id. In this example, attendant 600 selects button 712 inorder to print a receipt to provide the customer with a record of thisinformation.

In another embodiment, handheld device 400 comprises a card reader,similar to card reader 210 of fuel dispenser 200 (FIG. 2), in order toallow attendant 600 to receive payment card data via a card's magneticstripe rather than manually entering the account information using touchscreen 500 or numeric pad buttons 504. Because card readers are magneticreaders and do not require contact with the card, the airtightcharacteristics of handheld device 400 are maintained. As a result,handheld device 400 remains compliant with the ATEX Directives.

In this embodiment, the customer provides attendant 600 with a magneticstripe card, which is swiped using the card reader. Should the customerbe required to provide the PIN for the swiped card, the customer may doso using either numeric pad buttons 504 or a GUI comprising a virtualPIN pad presented by touch screen 500. Data representative of thefinancial information provided by the customer is transmitted byhandheld device 400 to site controller 308 via the wireless meshnetwork. The fueling process continues in a manner similar to thatdescribed above.

In another embodiment, handheld device 400 comprises a smart card readerin order to allow attendant 600 to handle transactions involving smartcards. As should be understood in the art, the use of smart cardsrequires contact between the card and the reader. In order to remainATEX-compliant, handheld device 400 comprises additional components toprevent any potential electrical discharge when a smart card comes intocontact with the smart card reader. For example, handheld device 400comprises an intrinsic safe barrier (“ISB”) operatively connected to thehandheld's smart card reader. Those of ordinary skill in the art shouldunderstand that an ISB limits the amount of current able to flow througha contact, such as the contact of the smart card reader. As a result,the ISB prevents the creation and discharge of electrical energy due tothe use of the smart card reader. As a result, handheld device 400remains in compliance with the ATEX Directives.

In this embodiment, the customer provides attendant 600 with a smartcard, which is read using the smart card reader. Handheld device 400transmits data representative of the information provided by the smartcard to site controller 308 via the wireless mesh network of fuelingenvironment 300. The process continues in a manner similar to thatdescribed above.

In another embodiment, handheld device 400 and fuel dispensers 200 a and200 b are configured to handle financial transactions for the fuelprovided by the dispensers. In such an embodiment, handheld device 400is configured to perform the functions and tasks previously performed bysite controller 308 associated with carrying out the financialtransactions. For instance, handheld device 400 may be configured toexecute financial transactions with the financial institution(s)connected to the WAN and to store data representative of the financialtransactions within memory 408 or on removable media via memory slot414. It should be understood that the fuel dispensers and the handhelddevice may continue to transmit data associated with the financialtransactions to site controller 308 for reporting or other purposes asexplained above.

In a scenario involving a prepaid cash transaction, attendant 600 mayauthorize a fuel dispenser, such as fuel dispenser 200 a, directly usinghandheld device 400 rather than via site controller 308. In one example,attendant 600 receives cash from a customer and enters the value of thecase into handheld device 400. In this embodiment, handheld device 400does not transmit data to site controller 308 representative of thefueling transaction such as the dispenser selected by the customer orthe cash provided to the attendant. Instead, the middleware executed byprocessing device 406 causes handheld device 400 to authorize directlythe fuel dispenser 200 a via the wireless mesh network.

It should be understood that, in an embodiment where handheld device 400is configured to handle financial transactions associated with thefueling process, the inclusion of user interface 202 (FIG. 2) withinfuel dispensers 200 may be unnecessary. That is, the fuel dispensers donot require any input devices in such an embodiment because thefinancial transactions associated with the dispensed are carried out byhandheld device 400. This is because handheld device 400 includes thecapabilities necessary to effect the transactions for the fuel providedby the dispensers. It should be understood that providing dispenserswithout a user interface may substantially reduce the manufacturing andmaintenance costs associated with the fuel dispensers.

In a scenario involving payment by a customer using a credit card,handheld device 400 receives the financial information from a magneticcard provided by the customer in the manner described above. Themiddleware of handheld device 400 determines the data necessary to sendto the financial institution based on the information received from thecard once it has been swiped through the handheld device's card reader.Handheld device 400 transmits the data via the wireless mesh network tothe financial institution. In an embodiment where wireless communicationdevice 100 e functions as a gateway, it handles communication of thedata with the financial institution and routes any returned data tohandheld device 400 via the wireless mesh network in a manner similar tothat described above. Based on the information transmitted to handhelddevice 400, processing device 406 determines whether to authorize fueldispenser 200 a, and, if so, transmits data representative of theauthorization to the fuel dispenser via the wireless mesh network. Theprocess then continues in a manner similar to that described above.

It should be understood that in an embodiment where handheld device 400and/or fuel dispensers 200 a and 200 b are configured to carry outtransactions directly with the financial institution, central facility302 may be unnecessary. That is, because fuel dispensers 200 a and 200 band handheld device 400 handle the financial transactions with therelevant financial institution directly, the requirement that thecomponents and devices located within central facility 302 be locatedwithin fueling environment 300 is eliminated.

In such an embodiment, handheld device 400 and fuel dispensers 200 a and200 b may be configured to transmit data associated with thetransactions conducted by the respective device to a reporting serverexternal to fueling environment 300. That is, after each transaction,handheld device 400 and/or fuel dispensers 200 a and 200 b transmit datarepresentative of the transaction to a remote reporting server via thewireless mesh network and the WAN. The remote reporting server maintainsa collection of information transmitted from the devices of fuelingenvironment 300 for reporting or other purposes as well as from devicesof other fueling environments. It should be understood that fueldispensers 200 a and 200 b and handheld device 400 may be configured totransmit only data that does not contain sensitive or confidentialinformation. As a result, the data transmissions, as well as thereceiving devices, would not be required to comply with certain securityregulations.

It should be further understood that other devices within fuelingenvironment 300 may also be configured to communicate with devices andcomputers located on the WAN in the same manner. For instance, themiddleware of wireless communication devices 100 may be configured toaccess and retrieve resources provided by remote servers connected tothe WAN. For instance, wireless communication devices 100 a and 100 bmay retrieve material from servers connected to the WAN and maintainedby third parties including driving directions, advertisements, andinformation regarding local amenities. Wireless communication devices100 a and 100 b provide the information to processing devices 204 to bepresented by display 208 (FIG. 2). In such an embodiment, fueldispensers 200 a and 200 b may be configured to communicate with theremote resources via the wireless mesh network and the WAN.

For another example, sensor 320 connected to UST 314 may determine thatthe volume of fuel in the tank has reached a relatively low level andoutputs data representative of the volume to wireless communicationdevice 100 h. In one embodiment, wireless communication device 100 htransmits the data to site controller 308 via the wireless mesh networkfor handling. Alternatively, wireless communication device 100 h isconfigured to transmit the relevant data to a service external tofueling environment 300 that is tasked with managing the amount of fuelwithin multiple fueling environments. For instance, a fueling managementdepot connected to the WAN may be responsible for management of the fuelsupplied to various fueling stations, including fueling environment 300.Wireless communication device 100 h transmits the relevant dataregarding the volume of fuel within UST 314 to the management depot viathe wireless mesh network and the WAN. The fueling management depot maybe configured to automatically direct or redirect a fueling tanker tofueling environment 300 in order to supply UST 314 with fuel.

In another embodiment, data from components within fueling environmentmay be routed to multiple recipients and/or destinations via thewireless mesh network. Referring to FIG. 6, for example, sensor 318outputs data if it determines that UST 312 has malfunctioned. Wirelesscommunication device 100 g is configured to transmit the datarepresentative of the malfunction to site controller 308, as well as toa device associated with a service technician external to fuelingenvironment 300, via the wireless mesh network. In one embodiment, sitecontroller 308 also handles transmission of the data to the servicetechnician's device. In another embodiment where wireless communicationdevice 100 e is configured to function as a gateway, gateway 100 ehandles transmission of the data to the service technician's device viathe WAN.

In the presently-described embodiment, the data transmitted by thewireless communication device 100 g may be transmitted via distinctpaths to both gateway 100 e and site controller 308. Alternatively, thedata may be transmitted via the same path until it reaches a specificpoint where the data is then routed via separate paths over the wirelessmesh network to gateway 100 e and to site controller 308. For instance,data intended for both recipients may be transmitted to gateway 100 e.The middleware of gateway 100 e instructs the gateway to route thetransmission to the service technician's device via the WAN and to routethe data to site controller 308 via the wireless mesh network.

In another embodiment, the components of fueling environment 300 may beconfigured to transmit data to the nearest handheld device, such ashandheld device 400, via the wireless mesh network. For instance, fueldispenser 200 b may be configured to transmit data representative of ahardware failure or malfunction to handheld device 400 via the wirelessmesh network. As a result, handheld device 400 presents attendant 600with the data, who is able to analyze, identify, and potentially resolvethe issue. For instance, fuel dispenser 200 b may be configured to senda transmission to handheld device 400 via the wireless mesh network whenthe receipt printer is out of paper. In this embodiment, the handhelddevice's GUI is configured to alert its operator when the problem hasbeen detected.

Referring to FIGS. 5 and 6, the GUIs displayed via touch screen 500 maybe configured to present buttons and indicia corresponding to otherdevices within fueling environment 300. For instance, the GUI maydisplay indicia representative of vending machine 322 and camera 324. Inthis embodiment, selecting the indicia provides information regardingthe operation of the respective device. For example, selecting theindicia associated with vending machine 322 may provide a status of themachine's inventory while selecting the indicia associated with camera324 may provide a feed to the camera's video footage.

In another embodiment, the wireless communication devices connected tocomponents within fueling environment 300 may be configured to transmitdata periodically indicating the status of the component to which thedevice is connected. For example, vending machine 322 may be configuredto output data representative of its inventory levels to wirelesscommunication device 100 i at predetermined intervals of time asdescribed above. Wireless communication device 100 i transmits thisinformation to site controller 308 or to handheld device 400. Wheninventory drops below a predefined level, the information transmitted bythe vending machine informs the intended recipient that the vendingmachine requires additional inventory. As a result, the operator of thereceiving device can refill the vending machine's inventory.Additionally, if wireless communication device 100 i has not receiveddata from the vending machine or if the intended recipient has notreceived data from wireless communication device 100 i for greater thana predefined amount of time, the intended recipient notifies itsoperator to inspect vending machine 322 and/or wireless communicationdevice 100 i to determine if either has malfunctioned or stoppedworking.

In another embodiment with reference to FIGS. 4 and 6, handheld device400 comprises an RF identification (“RFID”) reader configured to sendand receive radio signals to and from an RFID tag. In this embodiment,an RFID tag unique to each fuel dispenser of fueling environment 300 isplaced within the dispenser's interior. In order to authorize the fueldispenser for use, attendant 600 scans the RFID tag with the handhelddevice's RFID reader. The RFID reader transmits the information receivedfrom the RFID tag to processing device 406, which identifies the fueldispenser corresponding to the tag. Handheld device 400 thencommunicates with the fuel dispenser via the wireless mesh network andthe fueling process proceeds in a manner similar to that describedabove.

In another embodiment, handheld device 400 comprises a Bluetooth radiodevice configured to communicate with other Bluetooth devices locatedwithin fueling environment 300. In such an embodiment, dispensers 200 aand 200 b are each equipped with a Bluetooth device operativelyconnected to the dispenser's processing device and configured tocommunicate with other Bluetooth devices, such as the one in handhelddevice 400. In this embodiment, the handheld device and the dispenserscommunicate via a Bluetooth personal area network (“PAN”) in order toauthorize the fuel dispensers and to effect transactions for payment ofany fuel provided by the dispensers. In this embodiment, handheld device400 and dispensers 200 a and 200 b may still be configured tocommunicate with other devices both internal and external to fuelingenvironment 300 via the wireless mesh network in a manner similar tothat described above.

It should be understood by those of ordinary skill in the art thathandheld device 400 also operates as a node of the wireless mesh networkof fueling environment 300. Thus, handheld device 400 may be used toroute data transmitted via the wireless mesh network. For instance,wireless communication device 100 a may determine that it is unable tocommunicate with wireless communication device 100 e directly but may beable to communicate with it indirectly by transmitting the applicabledata via handheld device 400. After analyzing the data to determine itsintended destination, handheld device 400 transmits the data to wirelesscommunication device 100 e via the wireless mesh network, which mayinclude a direct line of transmission. Alternatively, handheld device400 may be unable to communicate directly with wireless communicationdevice 100 e due to environmental factors. In this instance, handhelddevice 400 transmits the data to wireless communication device 100 e viaone or more of the other nodes of the wireless mesh network.

Additionally, each handheld device stores data representative of thetransactions carried out by the handheld device and by each operator ofthe device. This provides a manager with the ability to create reportsfor each handheld device and for each operator regarding thetransactions managed by the handheld device or operator for the fuelingenvironment. In one embodiment, handheld device 400 transmits this datato site controller 308 via the wireless mesh network. Alternatively, thehandheld device stores this data on external media that has beeninserted into its memory slot 414.

It should be further understood that the middleware stored in memory andexecuted by the processing device of each wireless communication devicecreates a “plug and play” environment. That is, wireless communicationdevices and components equipped with such devices may be added tofueling environment 300 at any time without degrading the wireless meshnetwork. The middleware described above enables any additional device tocommunicate via the wireless mesh network of the fueling environment. Itshould be further understood that the conversion component enableslegacy or non-standard devices to communicate with the middleware, whichenables the legacy or non-standard devices to communicate with otherdevices via the wireless mesh network. Additionally, the fuelingenvironment described herein is scalable, meaning that devices may beadded to and removed from the fueling environment without affecting thewireless mesh network or the environment's other devices.

According to another embodiment, the present invention provides a lowcost yet very secure solution for vehicle identification, utilizing“transponder” technology. The system can also desirably ensure that thenozzle is actually in the vehicle's fuel tank during the whole refuelingprocess.

In particular, the proposed solution uses a handheld forecourtcontroller (as described above) enabled with Zigbee or the like. Thishandheld device may be installed on the nozzle by the operator and maycontain a two-antenna tag reader—able to read a tag installed on thenozzle and one installed on the vehicle near the tank opening. When thenozzle is inserted, the handheld can read the nozzle ID and the vehicleID, and access a remote database wirelessly so as to get theauthorization for that dispenser. Because the antennas will preferablyread only short distance, if the handheld is removed, or the nozzle isremoved from the tank, the handheld will detect this event andimmediately (e.g., via Zigbee) stop the transaction. Some advantages ofsuch a system are: (1) Installation is easier than any other knownsolution; (2) Power is within the handheld, which can be recharged; (3)Because the handheld is ATEX, no further approvals are required; (4)Tags on nozzle are inexpensive and simply be glued in place. (5) Vehicletags on vehicle are also inexpensive. (6) No physical wiring is requiredon vehicle or on site.

A mechanism can be provided to attach the handheld on the nozzle itself.The two transponder/proximity readers installed in the handheld can beconfigured such that the reading distance could be as short as desired.In such an embodiment, one reader will read underneath the handheld (toread a tag on the nozzle), whereas the other one can read on a side (toread the tag on the vehicle). The nozzle transponder can simply be gluedor otherwise attached to the side of the nozzle. The vehicle transpondercould be similarly installed in proximity of the car tank opening and insuch a position that it would be in the range of the handheld readeronce the nozzle with the piggy back handheld is close enough or actuallyinside the tank opening.

Once the operator has installed the handheld on the nozzle, the nozzleis inserted into the tank, as normally done. The handheld wouldimmediately read the tag on the vehicle, send via Zigbee a message tothe existing forecourt controller (equipped with a Zigbee receiver)containing the tag content, and consequently activate a new transactionfor the dispenser requiring the authorization. If the nozzle or thehandheld are removed, the transaction is stopped.

While one or more preferred embodiments of the invention have beendescribed above, it should be understood that any and all equivalentrealizations of the present invention are included within the scope andspirit thereof. The embodiments depicted are presented by way of exampleonly and are not intended as limitations upon the present invention.Thus, it should be understood by those of ordinary skill in this artthat the present invention is not limited to these embodiments sincemodifications can be made. Therefore, it is contemplated that any andall such embodiments are included in the present invention as may fallwithin the scope of the appended claims and their equivalents.

What is claimed is:
 1. A handheld device for use in a retail fuelingenvironment, said handheld device comprising: a housing; a touchscreendisplay; circuitry located within said housing, said circuitry includinga processor implementing a graphical user interface on said touchscreendisplay; and said circuitry further including wireless communicationcircuitry implementing a middleware program such that said handhelddevice functions as a node in a wireless mesh network in said retailfueling environment.
 2. A handheld device as set forth in claim 1,wherein said processor allows said handheld device to control operationof at least one fuel dispenser in said retail fueling environment viasaid wireless mesh network.
 3. A handheld device as set forth in claim2, further comprising an RFID reader for reading an RFID associated withsaid at least one fuel dispenser.
 4. A handheld device as set forth inclaim 2, wherein real-time fueling information is shown on saidtouchscreen display during a fueling transaction at said fuel dispenser.